Dynomotion

Group: DynoMotion Message: 6533 From: fireup_kev Date: 1/21/2013
Subject: Fire M-Code along a G1 linear move
How Can I trigger an M-Code to turn on with-in a linear move?

I have something like this

N1 G1 X1.
N2 M3
N3 X2.

I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0

Kevin
Group: DynoMotion Message: 6535 From: Tom Kerekes Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
Hi Kevin,

There is a way to embed IO commands into the coordinated motion buffer so they occur synchronized with the motion.

How do you have the M3 code configured?  If it is a simple IO command it should be automatically embedded.  If it is running a C Program it will not.

Regards
TK


Group: DynoMotion Message: 6536 From: himykabibble Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
You don't say whether you're running Mach3 or KMotionCNC. If your M3 function is set to "Exec/Wait", it should do exactly what you want. Sounds like you have it set to "Execute Program"?

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, "fireup_kev" wrote:
>
> How Can I trigger an M-Code to turn on with-in a linear move?
>
> I have something like this
>
> N1 G1 X1.
> N2 M3
> N3 X2.
>
> I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0
>
> Kevin
>
Group: DynoMotion Message: 6537 From: fireup_kev Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
The M3 is a simple IO command. When multiple moves are on the same linear path, it seems to be combined into one line, and then the M3 get's added and fired after the end of that linear path.

How do I embed IO commands into the coordinated motion to be fired at the desired point?

--- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
>
> Hi Kevin,
>
> There is a way to embed IO commands into the coordinated motion buffer so they occur synchronized with the motion.
>
> How do you have the M3 code configured?  If it is a simple IO command it should be automatically embedded.  If it is running a C Program it will not.
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: fireup_kev
> To: DynoMotion@yahoogroups.com
> Sent: Monday, January 21, 2013 10:37 AM
> Subject: [DynoMotion] Fire M-Code along a G1 linear move
>
>
>  
> How Can I trigger an M-Code to turn on with-in a linear move?
>
> I have something like this
>
> N1 G1 X1.
> N2 M3
> N3 X2.
>
> I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0
>
> Kevin
>
Group: DynoMotion Message: 6538 From: Tom Kerekes Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
Hi Kevin,

That sounds like a bug.  Could you set the Colinear Tolerance to 0 in the Trajectory Planner as a test to see it it solves the problem?

Another workaround might be to change the feed rate slightly (needs to be more than 1% difference).  So try:

N1 G1 X1.  F100
N2 M3
N3 X2. F102

Regards
TK

Group: DynoMotion Message: 6539 From: himykabibble Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
Tom,

This works as expected:

G1 X1 F10
M7
X0
M30

This does not:

G1 X1 F10
M7
X2
M30

In the first case, the M7 executes very close to X=1. In the second case, it never executes - I suspect it is executing at X=2, the gets immediately over-ridden by the M30.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
>
> Hi Kevin,
>
> That sounds like a bug.  Could you set the Colinear Tolerance to 0 in the Trajectory Planner as a test to see it it solves the problem?
>
> Another workaround might be to change the feed rate slightly (needs to be more than 1% difference).  So try:
>
>
> N1 G1 X1.  F100
> N2 M3
> N3 X2. F102
>
>
> Regards
> TK
>
>
>
> ________________________________
> From: fireup_kev
> To: DynoMotion@yahoogroups.com
> Sent: Monday, January 21, 2013 1:44 PM
> Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
>
>
>  
> The M3 is a simple IO command. When multiple moves are on the same linear path, it seems to be combined into one line, and then the M3 get's added and fired after the end of that linear path.
>
> How do I embed IO commands into the coordinated motion to be fired at the desired point?
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> >
> > Hi Kevin,
> >
> > There is a way to embed IO commands into the coordinated motion buffer so they occur synchronized with the motion.
> >
> > How do you have the M3 code configured?  If it is a simple IO command it should be automatically embedded.  If it is running a C Program it will not.
> >
> > Regards
> > TK
> >
> >
> >
> >
> > ________________________________
> > From: fireup_kev
> > To: DynoMotion@yahoogroups.com
> > Sent: Monday, January 21, 2013 10:37 AM
> > Subject: [DynoMotion] Fire M-Code along a G1 linear move
> >
> >
> >  
> > How Can I trigger an M-Code to turn on with-in a linear move?
> >
> > I have something like this
> >
> > N1 G1 X1.
> > N2 M3
> > N3 X2.
> >
> > I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0
> >
> > Kevin
> >
>
Group: DynoMotion Message: 6540 From: Tom Kerekes Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
Hi Ray,

Thanks.  That would be as expected.  The first is not collinear (I assume you are starting from zero) it is a 180 degree corner.

How about:

G1 X1 F10
M7
X2 F10.2
M30

Regards
TK


Group: DynoMotion Message: 6541 From: fireup_kev Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
That workaround works but changing the feed rate form 10 to F50 and F10.2 to F50.2 does not work. Also changing F10.2 to F10.001 delays the M-Code from firing a little bit right after X1.0 ...

These are the workaround that works:

G1 X1 F10
G4P0
M3 (or M7)
X2

or

Setting collinear tolerance to 0 and...

G1 X1 Y.0 F10
M3 (or M7)
X2 Y0.00001


The first one having the side effect of slowing down and stopping at X1 before continuing.

Kevin


--- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
>
> Hi Ray,
>
> Thanks.  That would be as expected.  The first is not collinear (I assume you are starting from zero) it is a 180 degree corner.
>
> How about:
>
>
> G1 X1 F10
> M7
> X2 F10.2
> M30
>
>
> Regards
> TK
>
>
>
> ________________________________
> From: himykabibble
> To: DynoMotion@yahoogroups.com
> Sent: Monday, January 21, 2013 2:39 PM
> Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
>
>
>  
> Tom,
>
> This works as expected:
>
> G1 X1 F10
> M7
> X0
> M30
>
> This does not:
>
> G1 X1 F10
> M7
> X2
> M30
>
> In the first case, the M7 executes very close to X=1. In the second case, it never executes - I suspect it is executing at X=2, the gets immediately over-ridden by the M30.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> >
> > Hi Kevin,
> >
> > That sounds like a bug.  Could you set the Colinear Tolerance to 0 in the Trajectory Planner as a test to see it it solves the problem?
> >
> > Another workaround might be to change the feed rate slightly (needs to be more than 1% difference).  So try:
> >
> >
> > N1 G1 X1.  F100
> > N2 M3
> > N3 X2. F102
> >
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: fireup_kev
> > To: DynoMotion@yahoogroups.com
> > Sent: Monday, January 21, 2013 1:44 PM
> > Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
> >
> >
> >  
> > The M3 is a simple IO command. When multiple moves are on the same linear path, it seems to be combined into one line, and then the M3 get's added and fired after the end of that linear path.
> >
> > How do I embed IO commands into the coordinated motion to be fired at the desired point?
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > >
> > > Hi Kevin,
> > >
> > > There is a way to embed IO commands into the coordinated motion buffer so they occur synchronized with the motion.
> > >
> > > How do you have the M3 code configured?  If it is a simple IO command it should be automatically embedded.  If it is running a C Program it will not.
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: fireup_kev
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Monday, January 21, 2013 10:37 AM
> > > Subject: [DynoMotion] Fire M-Code along a G1 linear move
> > >
> > >
> > >  
> > > How Can I trigger an M-Code to turn on with-in a linear move?
> > >
> > > I have something like this
> > >
> > > N1 G1 X1.
> > > N2 M3
> > > N3 X2.
> > >
> > > I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0
> > >
> > > Kevin
> > >
> >
>
Group: DynoMotion Message: 6542 From: himykabibble Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
Tom,

I thought one of the basic rules of G-code was that the blocks execute in order. Things on a single line may not necessarily operate in the order specified, but two consecutive lines should always execute in the order in which they appear in the G-code. Is that not correct?

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
>
> Hi Ray,
>
> Thanks.  That would be as expected.  The first is not collinear (I assume you are starting from zero) it is a 180 degree corner.
>
> How about:
>
>
> G1 X1 F10
> M7
> X2 F10.2
> M30
>
>
> Regards
> TK
>
>
>
> ________________________________
> From: himykabibble
> To: DynoMotion@yahoogroups.com
> Sent: Monday, January 21, 2013 2:39 PM
> Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
>
>
>  
> Tom,
>
> This works as expected:
>
> G1 X1 F10
> M7
> X0
> M30
>
> This does not:
>
> G1 X1 F10
> M7
> X2
> M30
>
> In the first case, the M7 executes very close to X=1. In the second case, it never executes - I suspect it is executing at X=2, the gets immediately over-ridden by the M30.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> >
> > Hi Kevin,
> >
> > That sounds like a bug.  Could you set the Colinear Tolerance to 0 in the Trajectory Planner as a test to see it it solves the problem?
> >
> > Another workaround might be to change the feed rate slightly (needs to be more than 1% difference).  So try:
> >
> >
> > N1 G1 X1.  F100
> > N2 M3
> > N3 X2. F102
> >
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: fireup_kev
> > To: DynoMotion@yahoogroups.com
> > Sent: Monday, January 21, 2013 1:44 PM
> > Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
> >
> >
> >  
> > The M3 is a simple IO command. When multiple moves are on the same linear path, it seems to be combined into one line, and then the M3 get's added and fired after the end of that linear path.
> >
> > How do I embed IO commands into the coordinated motion to be fired at the desired point?
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > >
> > > Hi Kevin,
> > >
> > > There is a way to embed IO commands into the coordinated motion buffer so they occur synchronized with the motion.
> > >
> > > How do you have the M3 code configured?  If it is a simple IO command it should be automatically embedded.  If it is running a C Program it will not.
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: fireup_kev
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Monday, January 21, 2013 10:37 AM
> > > Subject: [DynoMotion] Fire M-Code along a G1 linear move
> > >
> > >
> > >  
> > > How Can I trigger an M-Code to turn on with-in a linear move?
> > >
> > > I have something like this
> > >
> > > N1 G1 X1.
> > > N2 M3
> > > N3 X2.
> > >
> > > I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0
> > >
> > > Kevin
> > >
> >
>
Group: DynoMotion Message: 6543 From: himykabibble Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
Tom,

In fact, per the RS274 spec, even if the M7 appears on the SAME line as a G0-G3 the M7 should be executed BEFORE the G0-G3, regardless of its position on the line. That would certainly strongly imply that if they are on separate lines, the M7 should execute first if the line it is on precedes line containing the G0-G3.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
>
> Hi Ray,
>
> Thanks.  That would be as expected.  The first is not collinear (I assume you are starting from zero) it is a 180 degree corner.
>
> How about:
>
>
> G1 X1 F10
> M7
> X2 F10.2
> M30
>
>
> Regards
> TK
>
>
>
> ________________________________
> From: himykabibble
> To: DynoMotion@yahoogroups.com
> Sent: Monday, January 21, 2013 2:39 PM
> Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
>
>
>  
> Tom,
>
> This works as expected:
>
> G1 X1 F10
> M7
> X0
> M30
>
> This does not:
>
> G1 X1 F10
> M7
> X2
> M30
>
> In the first case, the M7 executes very close to X=1. In the second case, it never executes - I suspect it is executing at X=2, the gets immediately over-ridden by the M30.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> >
> > Hi Kevin,
> >
> > That sounds like a bug.  Could you set the Colinear Tolerance to 0 in the Trajectory Planner as a test to see it it solves the problem?
> >
> > Another workaround might be to change the feed rate slightly (needs to be more than 1% difference).  So try:
> >
> >
> > N1 G1 X1.  F100
> > N2 M3
> > N3 X2. F102
> >
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: fireup_kev
> > To: DynoMotion@yahoogroups.com
> > Sent: Monday, January 21, 2013 1:44 PM
> > Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
> >
> >
> >  
> > The M3 is a simple IO command. When multiple moves are on the same linear path, it seems to be combined into one line, and then the M3 get's added and fired after the end of that linear path.
> >
> > How do I embed IO commands into the coordinated motion to be fired at the desired point?
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > >
> > > Hi Kevin,
> > >
> > > There is a way to embed IO commands into the coordinated motion buffer so they occur synchronized with the motion.
> > >
> > > How do you have the M3 code configured?  If it is a simple IO command it should be automatically embedded.  If it is running a C Program it will not.
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: fireup_kev
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Monday, January 21, 2013 10:37 AM
> > > Subject: [DynoMotion] Fire M-Code along a G1 linear move
> > >
> > >
> > >  
> > > How Can I trigger an M-Code to turn on with-in a linear move?
> > >
> > > I have something like this
> > >
> > > N1 G1 X1.
> > > N2 M3
> > > N3 X2.
> > >
> > > I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0
> > >
> > > Kevin
> > >
> >
>
Group: DynoMotion Message: 6544 From: fireup_kev Date: 1/21/2013
Subject: Re: Fire M-Code along a G1 linear move
I was able to fix the bug myself my modifying TrajectoryPlanner.cpp
on line 162. I changed "if (CombineSegments(MaxCombineLength))" to
"if (CombineSegments(MaxCombineLength) || nspecial_cmds > 0)"

I'm not sure if this is the right place to change it as I have not done enough testing to see if it may cause other side-effects.

Thanks,
Kevin

--- In DynoMotion@yahoogroups.com, "fireup_kev" wrote:
>
> That workaround works but changing the feed rate form 10 to F50 and F10.2 to F50.2 does not work. Also changing F10.2 to F10.001 delays the M-Code from firing a little bit right after X1.0 ...
>
> These are the workaround that works:
>
> G1 X1 F10
> G4P0
> M3 (or M7)
> X2
>
> or
>
> Setting collinear tolerance to 0 and...
>
> G1 X1 Y.0 F10
> M3 (or M7)
> X2 Y0.00001
>
>
> The first one having the side effect of slowing down and stopping at X1 before continuing.
>
> Kevin
>
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> >
> > Hi Ray,
> >
> > Thanks.  That would be as expected.  The first is not collinear (I assume you are starting from zero) it is a 180 degree corner.
> >
> > How about:
> >
> >
> > G1 X1 F10
> > M7
> > X2 F10.2
> > M30
> >
> >
> > Regards
> > TK
> >
> >
> >
> > ________________________________
> > From: himykabibble
> > To: DynoMotion@yahoogroups.com
> > Sent: Monday, January 21, 2013 2:39 PM
> > Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
> >
> >
> >  
> > Tom,
> >
> > This works as expected:
> >
> > G1 X1 F10
> > M7
> > X0
> > M30
> >
> > This does not:
> >
> > G1 X1 F10
> > M7
> > X2
> > M30
> >
> > In the first case, the M7 executes very close to X=1. In the second case, it never executes - I suspect it is executing at X=2, the gets immediately over-ridden by the M30.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > >
> > > Hi Kevin,
> > >
> > > That sounds like a bug.  Could you set the Colinear Tolerance to 0 in the Trajectory Planner as a test to see it it solves the problem?
> > >
> > > Another workaround might be to change the feed rate slightly (needs to be more than 1% difference).  So try:
> > >
> > >
> > > N1 G1 X1.  F100
> > > N2 M3
> > > N3 X2. F102
> > >
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: fireup_kev
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Monday, January 21, 2013 1:44 PM
> > > Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
> > >
> > >
> > >  
> > > The M3 is a simple IO command. When multiple moves are on the same linear path, it seems to be combined into one line, and then the M3 get's added and fired after the end of that linear path.
> > >
> > > How do I embed IO commands into the coordinated motion to be fired at the desired point?
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > > >
> > > > Hi Kevin,
> > > >
> > > > There is a way to embed IO commands into the coordinated motion buffer so they occur synchronized with the motion.
> > > >
> > > > How do you have the M3 code configured?  If it is a simple IO command it should be automatically embedded.  If it is running a C Program it will not.
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: fireup_kev
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Monday, January 21, 2013 10:37 AM
> > > > Subject: [DynoMotion] Fire M-Code along a G1 linear move
> > > >
> > > >
> > > >  
> > > > How Can I trigger an M-Code to turn on with-in a linear move?
> > > >
> > > > I have something like this
> > > >
> > > > N1 G1 X1.
> > > > N2 M3
> > > > N3 X2.
> > > >
> > > > I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0
> > > >
> > > > Kevin
> > > >
> > >
> >
>
Group: DynoMotion Message: 6546 From: Tom Kerekes Date: 1/22/2013
Subject: Re: Fire M-Code along a G1 linear move
Hi Ray,

This is a bug.  It comes about when the Trajectory Planner combines multiple GCode blocks together using the collinear tolerance.  You could imagine several microscopic GCode blocks being replaced by one motion (this happens more often than one would expect).  If one of the GCode blocks contains an MCode it ends up incorrectly occurring before or after the motion. 

We will try to fix this.

Regards
TK

Group: DynoMotion Message: 6547 From: Tom Kerekes Date: 1/22/2013
Subject: Re: Fire M-Code along a G1 linear move
Hi Kevin,

Very Clever.  But I think doing that would mean one special command would mean that nothing else ever gets combined.  I'm hoping to find a way were things before or after the special command can still be combined.

Actually on a related issue is the Corner Rounding.  On a path with a waypoint that has a slight angle, an arc (multiple segments) will be inserted into the corner.  If the corner has an associated Special Command then currently it probably occurs before or after the arc.  I suppose toward the middle of the arc would be more appropriate.

Thanks
TK
Group: DynoMotion Message: 6582 From: fireup_kev Date: 1/24/2013
Subject: Re: Fire M-Code along a G1 linear move
Tom,

Have you come up with a good solution for this? How about reserving a special M-Code or G-Code to toggle between combining segments or not? Usually when this feature is needed the G-Code is pretty "clean" and compact, the combine feature is not required. Having a way for the user to turn on and off this feature will make it more robust.

Kevin

--- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
>
> Hi Kevin,
>
> Very Clever.  But I think doing that would mean one special command would mean that nothing else ever gets combined.  I'm hoping to find a way were things before or after the special command can still be combined.
>
> Actually on a related issue is the Corner Rounding.  On a path with a waypoint that has a slight angle, an arc (multiple segments) will be inserted into the corner.  If the corner has an associated Special Command then currently it probably occurs before or after the arc.  I suppose toward the middle of the arc would be more appropriate.
>
>
> Thanks
> TK
>
>
> ________________________________
> From: fireup_kev
> To: DynoMotion@yahoogroups.com
> Sent: Monday, January 21, 2013 9:57 PM
> Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
>
>
>  
> I was able to fix the bug myself my modifying TrajectoryPlanner.cpp
> on line 162. I changed "if (CombineSegments(MaxCombineLength))" to
> "if (CombineSegments(MaxCombineLength) || nspecial_cmds > 0)"
>
> I'm not sure if this is the right place to change it as I have not done enough testing to see if it may cause other side-effects.
>
> Thanks,
> Kevin
>
> --- In DynoMotion@yahoogroups.com, "fireup_kev" wrote:
> >
> > That workaround works but changing the feed rate form 10 to F50 and F10.2 to F50.2 does not work. Also changing F10.2 to F10.001 delays the M-Code from firing a little bit right after X1.0 ...
> >
> > These are the workaround that works:
> >
> > G1 X1 F10
> > G4P0
> > M3 (or M7)
> > X2
> >
> > or
> >
> > Setting collinear tolerance to 0 and...
> >
> > G1 X1 Y.0 F10
> > M3 (or M7)
> > X2 Y0.00001
> >
> >
> > The first one having the side effect of slowing down and stopping at X1 before continuing.
> >
> > Kevin
> >
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > >
> > > Hi Ray,
> > >
> > > Thanks.  That would be as expected.  The first is not collinear (I assume you are starting from zero) it is a 180 degree corner.
> > >
> > > How about:
> > >
> > >
> > > G1 X1 F10
> > > M7
> > > X2 F10.2
> > > M30
> > >
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: himykabibble
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Monday, January 21, 2013 2:39 PM
> > > Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
> > >
> > >
> > >  
> > > Tom,
> > >
> > > This works as expected:
> > >
> > > G1 X1 F10
> > > M7
> > > X0
> > > M30
> > >
> > > This does not:
> > >
> > > G1 X1 F10
> > > M7
> > > X2
> > > M30
> > >
> > > In the first case, the M7 executes very close to X=1. In the second case, it never executes - I suspect it is executing at X=2, the gets immediately over-ridden by the M30.
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > > >
> > > > Hi Kevin,
> > > >
> > > > That sounds like a bug.  Could you set the Colinear Tolerance to 0 in the Trajectory Planner as a test to see it it solves the problem?
> > > >
> > > > Another workaround might be to change the feed rate slightly (needs to be more than 1% difference).  So try:
> > > >
> > > >
> > > > N1 G1 X1.  F100
> > > > N2 M3
> > > > N3 X2. F102
> > > >
> > > >
> > > > Regards
> > > > TK
> > > >
> > > >
> > > >
> > > > ________________________________
> > > > From: fireup_kev
> > > > To: DynoMotion@yahoogroups.com
> > > > Sent: Monday, January 21, 2013 1:44 PM
> > > > Subject: [DynoMotion] Re: Fire M-Code along a G1 linear move
> > > >
> > > >
> > > >  
> > > > The M3 is a simple IO command. When multiple moves are on the same linear path, it seems to be combined into one line, and then the M3 get's added and fired after the end of that linear path.
> > > >
> > > > How do I embed IO commands into the coordinated motion to be fired at the desired point?
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > > > >
> > > > > Hi Kevin,
> > > > >
> > > > > There is a way to embed IO commands into the coordinated motion buffer so they occur synchronized with the motion.
> > > > >
> > > > > How do you have the M3 code configured?ÃÆ'‚  If it is a simple IO command it should be automatically embedded.ÃÆ'‚  If it is running a C Program it will not.
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: fireup_kev
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Monday, January 21, 2013 10:37 AM
> > > > > Subject: [DynoMotion] Fire M-Code along a G1 linear move
> > > > >
> > > > >
> > > > > ÃÆ'‚ 
> > > > > How Can I trigger an M-Code to turn on with-in a linear move?
> > > > >
> > > > > I have something like this
> > > > >
> > > > > N1 G1 X1.
> > > > > N2 M3
> > > > > N3 X2.
> > > > >
> > > > > I would like the M3 to fire when X gets to 1.0 but it gets blended with the third line (X2.) and M3 gets fired when X gets to 2.0
> > > > >
> > > > > Kevin
> > > > >
> > > >
> > >
> >
>
Group: DynoMotion Message: 6587 From: Tom Kerekes Date: 1/24/2013
Subject: Re: Fire M-Code along a G1 linear move
Hi Kevin,

That might be a good idea. It might be good to have regardless of this issue.  But no I don't have a solution yet.  I want to think it through.  You have a workaround right?

Thanks
TK